Skip to content

Rebuild the GitHub Action on the commands and the pull-request report - #84

Merged
Mpdreamz merged 2 commits into
mainfrom
action
Nov 14, 2026
Merged

Mpdreamz merged 2 commits into
mainfrom
action

Conversation

@Mpdreamz

Copy link
Copy Markdown
Contributor

uses: nullean/assembly-differ@v1 now compares a pull request's libraries with their last release, comments, sets the release-drafter label, and fails on a breaking change until the pull request gets the breaking-allowed label. The old inputs still work.

Prompt summary: The action's arguments are hard to use, and there is no clear path to hooking it up to pull requests. It should set the breaking label, fail, and pass once a configurable allow label is added: the author makes a breaking change, the action detects it, labels it and fails, the author adds the allow label, and the next run succeeds.

Why

The action ran assembly-differ diff <first> <second> <args> in a container: two provider specs and a free-form string. It had no outputs and did nothing on the pull request. Wiring it up took a hand-written workflow around it.

What

A composite action

It installs the tool with dotnet tool, so the solution mode can read the projects with the SDK the build already set up. Without package it runs projects, comparing every library of the solution in working-directory with its latest release; with package it runs release on that .nupkg. The report goes to api-changes.json, and pull-request puts it on the pull request.

Typed inputs and outputs

The inputs are package, projects, target, framework, fail-on (default major), allow-label (default breaking-allowed), the three label names, comment, labels, working-directory, token and version. The outputs are suggested-change, breaking-changes and report. Every input reaches the scripts through environment variables, never through ${{ }} inside run:, so zizmor reports no findings. The tool is called by path, not added to GITHUB_PATH.

The old inputs

first, second and args still run diff in ghcr.io/nullean/assembly-differ:edge, with the workspace mounted as before, and print a deprecation warning.

README

A workflow to copy, with the labeled and unlabeled events that make adding the allow label rerun the check, a table of inputs, and what happens on a pull request from a fork.

Verify

zizmor --min-severity low action.yml

I ran the steps' scripts locally against argh's solution and a Proc package, with a stand-in for the installed tool. The solution suggested None and passed. The package suggested Major with 5 breaking changes, set the outputs, and exited 4 under fail-on: major.

Out of scope: The action installs the latest released tool, and pull-request --fail-on --allow-label arrives in #83. So the new path works from the first release that carries #83, which is planned as 1.0, the release that also creates the v1 tag.

🤖 Generated with Claude Code

The action ran diff with two provider specs and a free-form args string,
and did nothing on the pull request. It now installs the tool, compares the
solution's libraries or a package, and runs pull-request: comment, release
label, and fail-on with the breaking-allowed label. Inputs are typed and it
has outputs. The old first, second and args inputs still run diff in the
container image, with a deprecation warning.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@Mpdreamz Mpdreamz added the feature A new capability (minor bump) label Nov 14, 2026
@Mpdreamz
Mpdreamz merged commit 288367e into main Nov 14, 2026
6 checks passed
@Mpdreamz
Mpdreamz deleted the action branch November 14, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature A new capability (minor bump)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant